Working on selected configurations of a team project

Development teams are usually split up into groups of programmers who are responsible for a particular aspect of a project. For example, after releasing a version of your software product, you might choose to split your team into two sub-teams: one responsible for developing the product further (Team A), and another responsible for fixing the bugs found in the product (Team B). In terms of the files maintained in your Repository, Team A would work on the main (trunk) configuration of your software system, and Team B would work on a branch configuration. At some time in the future, the most current versions of the two configurations are merged with each other.
To assist project leaders in making sure that team members are working on the correct configurations of a software system, working environments can specify a Default Configuration. This is the configuration of your software system that your team members work on, and is used as the default value for version control operations such as check-in and check-out.
Default Configurations and SNiFF+'s branch support are discussed in the Chapter Version Control.